Building an image

Follow us on:

Share This Page

Facebook Twitter LinkedIn WhatsApp Email Copy Link

Close

Send Email Using

Gmail (Web) Thunderbird (default mail app)

Close

NXP i.MX95 Technical Guide

< >

NXP i.MX95

Table of Contents [Sticky]

• Introduction
  • What is i.MX95?
  • Why choosing RidgeRun for your i.MX95 software?
• Carrier Boards
  • Verdin Development Board
    • Yocto Support
      • Setup Yocto Environment
      • Building an image
      • Flashing the Board
      • Getting into the Board
    • Toradex Easy Installer
      • Hardware Setup
      • Installing a pre-built image using GUI
      • Offline Installation of a pre-built image using GUI
      • Re-Installing Toradex Easy Installer
    • Torizon OS
      • Overview
      • Installing Torizon OS Pre-Built Image
      • Containers in Torizon OS
      • Torizon Core Builder
      • Customizing an image with Torizon Core Builder
• GStreamer Support
  • Capture & Recording
  • Playback Audio & Video
  • Snapshot
  • Display
  • Video Streaming
    • UDP & RTP Streaming
• Multimedia Support
  • Audio
  • Video Capture
    • Capture Subsystem
    • Testing Camera Capture
  • Video Processing Unit-VPU
• Neural Processing Unit-NPU
  • eIQ Neutron NPU overview
  • Machine Learning Software Stack
  • Enabling NPU software with Yocto
  • Testing ML demos
• FAQ
• Contact Us

Modify the existing configuration

Since this image is directed to run on a Verdin i.MX95 SOM, we need to modify the configuration accordingly. In build/conf/local.conf, ensure the machine is set to:

MACHINE = "verdin-imx95"

Since Verdin iMX95 is NXP-based, you must accept the Freescale/NXP EULA. Appending this line at the end of the local.conf:

 ACCEPT_FSL_EULA = "1"

If this is not added, the build will fail when building NXP components.

By default, the distribution is usually set automatically (commonly tdx-xwayland). You may override it in local.conf if needed:

 DISTRO ?= "tdx-xwayland"

Available distro variants include:

• tdx-xwayland – Downstream vendor kernel without PREEMPT_RT

• tdx-xwayland-rt – Downstream vendor kernel with PREEMPT_RT

• tdx-xwayland-upstream – Mainline kernel without PREEMPT_RT

• tdx-xwayland-upstream-rt – Mainline kernel with PREEMPT_RT

For most use cases, the default is sufficient.

Build the Image

Toradex provides two reference image variants for evaluation purposes.

Reference Minimal Image

Image name:

 tdx-reference-minimal-image 

Features:

• Headless system (no graphical interface)
• systemd as init system
• connman network manager
• Basic command-line package group

Build the image:

cd build 
bitbake tdx-reference-minimal-image

Reference Multimedia Image

Image name:

 tdx-reference-multimedia-image 

Includes everything from the Minimal image, plus:

• Weston / Wayland + XWayland
• Qt graphical framework
• GStreamer multimedia framework
• V4L2 camera framework
• Graphical and Qt package groups

Build the image:

cd build 
bitbake -k tdx-reference-multimedia-image

Notes:

• The first build may take several hours.

• Subsequent builds are faster due to caching.

• -k option is used to keep the build process even after a package failed.

Final Result

After a successful build, you should see multiple files in:

 build/deploy/images/verdin-imx95/ 

Among them, the most relevant files for deployment and usage are the following:

Toradex Easy Installer Image (Recommended for eMMC Flashing)

• Verdin-iMX95_Reference-Minimal-Image-Tezi_<version>.tar
• Verdin-iMX95_Reference-Minimal-Image-Tezi.tar

This is the image used with Toradex Easy Installer (TEZI).

SD Card Image

• Verdin-iMX95_Reference-Minimal-Image.wic.gz
• Verdin-iMX95_Reference-Minimal-Image.wic.bmap

This image is used to boot directly from an SD card.

Info

It is recommended to follow the TEZI workflow

Back to top ↑ < >